2.5.141 Maintenance Release Notes

In This Topic...

Enhancements

  • To aid users when building Billing dashboards, an enhancement has been made to allow direct access to a Bill to Party from a configured hyperlink in a dashboard. Previously, to access a Bill to Party, the user had to select the Billing Entity first or an error message could be returned. After this enhancement, the Bill to Party can be accessed independent of its Billing Entity.

  • Previously, the system did not show the details of the Cash Receipt Allocation in the Receipt Allocation panel when the system used the automatic On Account Balance to pay the outstanding invoices. A new Type column has been added to the Receipt Allocation panel to show whether it is a Refund or Account Balance Allocation type. Additionally, each receipt in the On Account allocation will hyperlink to the Receipt Information screen.

    Please note that the Refund panel name has been changed to Refund/on Account allocation.

Bug Fixes

  • Previously, a server error appeared when trying to create an Endorsement on a policy with a file loaded for the File Upload Control that had an out-of-sequence Endorsement. This server error occurred when file upload contents were loaded during the field copying and the GUID of the loaded files did not match what was saved in the TransactionXML. A code fix to prevent this error has been implemented, in which a link is placed upon the file uploaded rather than the deleted file. As a result, the error message no longer appears.

  • Previously, in a custom field, the Default Formula of a Calculated Field could not be pushed to the Field Path of the Bind To section. This bug occurred when a field was configured as non-calculated and contained BindTo set to a standard field such as Claim/DateofLoss or Policy/MasterCover. As a result, the field value would not be updated during a Save event. A bug fix has been implemented and non-calculated fields can now be bound to Standard Fields.

  • Previously, an Office Admin user would see the Policy Term displayed in the Submission/Policy List screen, but they would not see the term's Audit Trail. This occurred because the logic used to validate the scope in the Policy Search was different from that of the Audit Trail screen. A fix has been implemented in which the Policy Transaction scope is used for both the Audit Trail screen and the Policy Transaction scope.

  • Previously, the Data Table Web Service failed if the data contained an Ampersand (&). Following the 2.5.140 release, the Ampersand (&) will be encoded in the data and can be included in the Data Table Web Service.

  • Previously, when filtering Data Sources in the Data Source Configuration Management screen, a bug occurred when the columns of a Data Source used a Field or Constant Value containing code that was different from the Column code. As a result, the filters were not applied, and the WebAPI call returned every result. A code fix has been implemented, and Data Source returns now properly returns filtered results.

  • Previously, any user could call a method for Insurity Bridge Common API via Insurity Azure Gateway. Now, a fix has been implemented that allows only authorized users to call a method. If a user is not authorized, an error message will display "Error: Unauthorized User" after entering the field for user authorization.

    Note: For details, please contact your Insurity representative

  • Previously, General Ledger entries could have an Entry Date of a past Receipt Date after setting Reserve On Account Amount to Future Installments to No in the On Account Balance screen. Now, the date will update according to when the setting Reserve On Account Amount to Future Installments has been set to No.

  • Previously, when generating and manually invoicing a Premium Refund, additional General Ledger entries of Written Premium and Premium Account Receivables were created for the Premium Refund invoice. This occurred when users created, generated, and bound a direct bill policy with taxes and commission values, generated an invoice, and flat canceled the policy. Now, for this case, the two additional General Ledger entries of Written Premium and Premium Account Receivables are no longer created.

  • Previously, when users used the ContainsUserRole()function in a Calculated Field in a Policy Workflow, altered the assigned security role for a user, and published the workflow, the change in User Roles would not update timely in the User Profile. This occurred because roles are only updated when the User Name, First Name, and Last Name for the logged in user are empty. Now, roles are updated whenever there is a change or modification to a User Role.

  • Previously, once a New Business Transaction was created, quoted and bound with Deductible Charges applied, the newly created Deductible Invoice would not be available for selection in the Batch Receipt List grid for a Batch Receipt. A code fix has been implemented, and deductible invoices are now available in the Batch Receipt List grid upon creating a Deductible Charge.

  • Previously, if an Assured company code contained special characters, the company was not carried onto subsequent transactions. As a result, the newly created transaction would be without an Assured company. A fix has been implemented where special characters are encoded to be compatible with allowed characters in the URL, and the Assured code is then decoded for the Bridge API. Now the Assured code can be found successfully, and Assured code can be carried forward to subsequent transactions.

  • Previously, when users created an Out-of-Sequence Endorsement or an Adjustment in a void operation for a first endorsement, the Distributor Grid did not update, and the top-level fields were updating in the Transaction XML. Now, when performing an Out-of-Sequence Endorsement or Adjustment, the Distributor Grid fields and the top-level fields update.

  • Previously, when manually adding an Invoice in Batch Receipts using the Invoice Allocation grid, there was no option to see the details of the Charge Type in the grid. A new Charge Type column has been added under the Invoice Allocation grid to show the details of the charges for the respective Invoice.